home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dr. Windows 3
/
dr win3.zip
/
dr win3
/
PROGRAMR
/
CLIKBR15.ZIP
/
ADDENDA.DOC
next >
Wrap
Text File
|
1993-03-23
|
9KB
|
268 lines
Addenda.Doc
This file is the v1.5 addendum to the manual for ClickBar v1.0, and contains
information pertinent to the v1.5 maintenance release of ClickBar.
All manual references in this document are referring to the ClickBar.DOC
manual dated 18-Apr-92. This document is a supplement to that manual, a new
manual to be issued with the v2.0 upgrade.
Installation
────────────
Installation of ClickBar v1.5 is accomplished by means of a Setup.EXE
provided on the release diskette. All files from v1.0 may be deleted prior to
the v1.5 installation, if desired. Any needed files are on the v1.5
diskettes, and any files not needed are not loaded. Therefore, a cleaner
install would be to remove the WynApse subdirectory, start Windows, and run
Setup.exe.
WynBtn
──────
WynBtn.DLL is no longer supported by WynApse, and is not used in ClickBar,
therefore not necessary to the use of ClickBar.DLL or ClickDlg.DLL. It is
still used during Setup at this time, but then may be removed from the users
hard disk. WynBtn.h may also be removed.
BWCC.DLL
────────
In the same manner, ClickDlg no longer relies upon BWCC.DLL. Borland users
may still desire to use it for the 3D effects on the dialog boxes, but it is
not necessary for the proper execution of ClickBar. As you will see below,
BWCC.DLL is no longer loaded in TestClik.C, and TestClik.exe is virtually
identical to the v1.0 version.
As with WynBtn, BWCC is used during Setup, but is not required for the
operation of ClickBar.DLL or ClickDlg.DLL.
The removal of the need for the two DLLs results in less memory being used
during the execution of the utilities.
End-User Registration
─────────────────────
End-User Registration for v1.0 fails under Windows 3.1. This v1.5 maintenance
upgrade of ClickBar and ClickDlg addresses this problem. The developer
instructions for run-time registration on Page 7 of the manual are still
correct.
The only change necessary is to page 14 of the manual. It is not necessary to
deliver a WynApse.INI file to an end-user. This is taken care of in
ClickBar.DLL, while processing your registration name and number. The bottom
half of page 14, starting with the sentence:
"The only acceptable time to build ..."
is to be ignored.
Single-Image Bitmaps
────────────────────
The upgrade to single-image bitmaps intended for v2.0 has been pulled down to
this maintenance release. This brings the user a smaller DLL, and
easier-to-use custom button interface. Instead of having to produce two
images for a custom button, the developer only needs to produce a single,
flat image, and ClickBar v1.5 will 3D it in an up- and down-image format. Of
course, if there is a need for two images, that is still possible. ClickBar
will still provide the proper 3D effect, but will handle both images
provided. This is demonstrated in ClikTest.EXE with the VCR buttons, and one
of the large buttons on the "Pick" button palette in TestClik has a double
image.
Custom bitmaps are still bound-in to the users EXE as with v1.0, according to
the manual. If a double image is desired, the even/odd 1000/3000 naming
concept is still valid on page 11 of the manual. If a single image is
sufficient, ignore the need for the odd numbered '3000' button. If only one
is found, only one is used. If two are found, two are used. That's how simple
it is. Examples of using both types of buttons are found in TestClik.RC.
Button Profiles
───────────────
The only drawback to changing to single-image buttons is forcing users to
redraw current custom images. Remember each button only requires one image
now, so the job is cut in half. And, new buttons are not being produced, only
extracted from current ones.
───────────────
22x18 16 colors
This button profile requires a 17x13 flat image that will sit inside the 3D
borders. Cutting the 17x13 center from an existing button will suffice for
most custom images.
───────────────
25x22 16 colors
This button profile requires a 20x17 flat image that will sit inside the 3D
borders. Cutting the 20x17 center from an existing button will suffice for
most custom images.
───────────────
24x24 16 colors
This button profile requires a 19x19 flat image that will sit inside the 3D
borders. Cutting the 19x19 center from an existing button will suffice for
most custom images.
TestClik Changes
────────────────
The following detail changes made to TestClik code for v1.5. Some of the
changes are Windows 3.1, some are ClickBar v1.5.
────────────
TestClik.mak
bwcc.lib was added to TestClik.mak. For non-Borland programmers, remove this
line, and any other Borland references. Additionally, the make file was
modified to handle Windows 3.0/3.1 changes. Compiling with the Windows 3.1
compatible compilers (Microsoft and Borland, both) necessitate a few
additions to run under Windows 3.0. Specifically,
RC testclik.res testclik.exe
is changed to:
RC -30 testclik.res testclik.exe
and the help compiler should still compile using the 3.0-compatible compiler
because 3.1 help files are not compatible with Windows 3.0.
────────────
TestClik.Def
The only change to TestClik.Def was to the exports list. Instead of exporting
the dialog procedure 'TestClikDlgProc', now 'PickDlgProc' is exported. This
is a demo of a floating custom button palette.
──────────
TestClik.H
A few IDs have been removed from TestClik.H. These had to do with the setup
dialog box that was replaced by a button palette.
────────────
TestClik.Dlg
The "testclik" dialog box profile is removed in this version of TestClik. In
its place "Pick", a floating custom button palette is inserted. This is seen
as a grid of 8 custom profile #2 buttons. The "CLICK" profile is changed only
in that the Borland "BorShade" control is no longer used for the button
background. This colorization is now taken care of in ClickDlg.DLL.
───────────
TestClik.RC
TestClik.RC has been modified to remove references to double-button images
except where desired. Also, the bitmap images for the button palette have
been added.
──────────
TestClik.C
TestClik.C has the majority of changes necessary. To compile with Windows 3.1
tools and run under Windows 3.0 requires the addition of:
#define WINVER 0x0300
prior to including windows.h
The other required change in this respect is the casting of:
WndClass.lpfnWndProc = WndProc;
to become:
WndClass.lpfnWndProc = (WNDPROC)WndProc;
this is found in the function WinMain, but is mentioned here for
completeness.
As explained above, references to WynBtn, or WynBtn.DLL are unnecessary in
v1.5 code.
'TestClikDlgProc' is no longer in TestClik, so any reference to it, and its
prototype will be missing.
The additional button palette 'PickDlgProc' has been added along with a
prototype for it.
The HWND declaration:
HANDLE hClickBar, hClickDlg;
has been moved to be global for proper execution of TestClik.exe, as has been
the declaration of
FARPROC lpfnDlgSetup;
This was pulled out global as will be shown later.
A major change was the removal of:
(*lpfnDlgSetup)(hWndMain);
from WinMain to the init section of WndProc. This was moved to prevent a
race condition with ClickDlg.DLL trying to operate on NULL window handles.
Users that have found DBWIN to display error messages with the debug version
of Microsoft Windows SDK will now find them to be clean with this change.
The message dispatch loop of WinMain was modified to accommodate the control
palette by changing the if statement from:
if (hWndDlg == 0 || !IsDialogMessage(hWndDlg, &msg))
to be:
if ((hWndDlg == 0 || !IsDialogMessage(hWndDlg, &msg)) &&
(hDlgModeLess == 0 || !IsDialogMessage(hDlgModeLess, &msg)))
As explained above, WM_NCCREATE is now captured in WndProc to properly make
the DlgSetup call. If this is captured, the DefWindowsProc should be executed
to allocate memory for the procedure